On 11/18/22 15:52, Wolfgang Schuster via ntg-context wrote:
> Pablo Rodriguez via ntg-context schrieb am 15.11.2022 um 16:06:
>> [...]
>> It looks like when --environment is used, ConTeXt assumes that the main
>> source only contains text. Which makes sense (at least, to me).
>
> The reason why
Pablo Rodriguez via ntg-context schrieb am 15.11.2022 um 16:06:
On 11/15/22 13:22, Denis Maier via ntg-context wrote:
Hi,
if I process an XML buffer, I’ve noticed I need to wrap the
\xmlprocessbuffer in a \starttext ... \stoptext pair.
[]
However, if I have the XML and the setups in dedicated
Denis Maier via ntg-context schrieb am 15.11.2022 um 13:22:
Hi,
if I process an XML buffer, I’ve noticed I need to wrap the
\xmlprocessbuffer in a \starttext ... \stoptext pair.
[...]
However, if I have the XML and the setups in dedicated files, there
seems to be no need for \starttext
> -Ursprüngliche Nachricht-
> Von: ntg-context Im Auftrag von Pablo
> Rodriguez via ntg-context
> Gesendet: Dienstag, 15. November 2022 16:07
> An: Denis Maier via ntg-context
> Cc: Pablo Rodriguez
> Betreff: Re: [NTG-context] Do environment files ad
On 11/15/22 13:22, Denis Maier via ntg-context wrote:
> Hi,
>
> if I process an XML buffer, I’ve noticed I need to wrap the
> \xmlprocessbuffer in a \starttext ... \stoptext pair.
> []
> However, if I have the XML and the setups in dedicated files, there
> seems to be n
Hi,
if I process an XML buffer, I've noticed I need to wrap the \xmlprocessbuffer
in a \starttext ... \stoptext pair.
%%%
\startbuffer[test]
a paragraph of text
another paragraph of text
\stopbuffer
\startxmlsetups xml:demo
\xmlsetsetup{\xmldocument}{document
Tue, Apr 03, 2018 ve 09:12:31AM +0200 Hans Hagen napsal(a):
# On 4/3/2018 12:02 AM, John Culleton wrote:
# >A reasonable approach to a Context file includes preliminary
# >information before the first printed page. My basic master file
# >looks like this :
# >
# > ...
#
# in the distribution
On 4/3/2018 12:02 AM, John Culleton wrote:
A reasonable approach to a Context file includes preliminary information
before the first printed page. My basic master file looks like this :
>
> ...
in the distribution there are a lot of manuals of which the setup
demonstrates ways to organize ...
From: "Wolfgang Schuster" <schuster.wolfg...@gmail.com>
Sent: Monday, April 2, 2018 2:41 PM
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: [NTG-context] Questions about \starttext
Tomas Ha
A reasonable approach to a Context file includes preliminary information before
the first printed page. My basic master file looks like this :
\input variables.tex\relax
\input layout.tex\relax
\input macros.tex\relax
\input fonts.tex\relax
\starttext\relax
%\showlayout
\startfrontmatter
Tomas Hala <mailto:tomas.h...@mendelu.cz>
20. März 2018 um 12:43
Hi all,
doing some tests I discovered two interesting facts.
The first is that commands \starttext and \stoptext do not behave as a
group.
Minimal example (tested on TL2015, TL2016, TL2017, current CTX from
the
Hi all,
doing some tests I discovered two interesting facts.
The first is that commands \starttext and \stoptext do not behave as a group.
Minimal example (tested on TL2015, TL2016, TL2017, current CTX from the Garden):
\starttext
text
\starttext
\bf text
\stoptext
text % this text
I thought that typesetting should start after \startext and that anything
before it should be ignored.
That is indeed the case with the following input:
ABC
\starttext
CONTENT
\stoptext
But add a \setupbodyfont and suddenly the ABC appears:
\setupbodyfont[lmodern]
ABC
\starttext
CONTENT
Am 16.04.2013 um 19:56 schrieb Meer, H. van der h.vanderm...@uva.nl:
I thought that typesetting should start after \startext and that anything
before it should be ignored.
That is indeed the case with the following input:
ABC
\starttext
CONTENT
\stoptext
But add a \setupbodyfont
Hello,
It would be nice, if \typesetbuffer wouldn't add anything to the buffer.
Here an example, where the outer \starttext ... \stoptext environment
deranges:
\starttext
\startbuffer[pdf-pages]
\setuppapersize[A7, landscape]
\showframe
\starttext
page 1 \page page 2
\stoptext
Am 30.01.2011 um 19:52 schrieb Peter Münster:
Hello,
It would be nice, if \typesetbuffer wouldn't add anything to the buffer.
Here an example, where the outer \starttext ... \stoptext environment
deranges:
Why, context ignores the inner starttext/stoptext pair.
Wolfgang
Wolfgang Schuster schuster.wolfg...@googlemail.com writes:
It would be nice, if \typesetbuffer wouldn't add anything to the buffer.
Here an example, where the outer \starttext ... \stoptext environment
deranges:
Why, context ignores the inner starttext/stoptext pair.
Wrong interpretation
On Sun, Jan 30, 2011 at 19:52, Peter Münster pmli...@free.fr wrote:
Hello,
It would be nice, if \typesetbuffer wouldn't add anything to the buffer.
Yep, I agree that. Don't know why need add something to buffer ?
Am 30.01.2011 um 20:23 schrieb Vnpenguin:
On Sun, Jan 30, 2011 at 19:52, Peter Münster pmli...@free.fr wrote:
Hello,
It would be nice, if \typesetbuffer wouldn't add anything to the buffer.
Yep, I agree that. Don't know why need add something to buffer ?
\typesetbuffer add \starttext
Am 30.01.2011 um 20:20 schrieb Peter Münster:
Nevertheless: are there situations, where the outer starttext/stoptext
could cause some trouble?
Don’t think so because when you use the project structure you have
\startproduct
\startcomponent
…
\stopcomponent
\startcomponent
…
\stopcomponent
20 matches
Mail list logo
